Enterprise Host Memory Buffer For DRAM-less SSD

ABSTRACT

A storage system includes one or more data storage devices, a PCIe switch coupled to the one or more data storage devices, and a controller unit coupled to the PCIe switch. The one or more data storage devices are DRAM-less. The controller unit includes a dynamic random access memory (DRAM) host memory buffer (HMB) controller and a DRAM pool or a controller memory buffer (CMB) controller, a root complex/port, and the DRAM pool. The DRAM pool includes one or more DRAM devices. The one or more data storage devices are configured to interact with the controller unit and store data to a DRAM of the DRAM pool of the controller unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of co-pending U.S. patentapplication Ser. No. 17/543,473, filed Dec. 6, 2021, which is hereinincorporated by reference.

BACKGROUND OF THE DISCLOSURE Field of the Disclosure

Embodiments of the present disclosure generally relate to DRAM-less datastorage devices, such as DRAM-less solid state drives (SSDs), and, morespecifically, using external storage devices via an interface betweenthe DRAM-less data storage device and a host device.

Description of the Related Art

Enterprise SSDs have specific requirements in order to integrate intodata center environments. For example, requirements may includepredictability and short latency for read operations and maintaining asame level of quality of service (QoS) for reads from any part of alogical address range of the SSD. Due to the requirements, logical blockaddress (LBA) to physical block address (PBA) (L2P) tables may be storedin DRAM, where the DRAM capacity may be in a 1:1000 ratio (e.g., 2 TBSSD=2 GB DRAM for L2P table caching). In some examples, the ratio may belarger (e.g., 1:2000) at the expense of performance due to increasedindirection. Thus, as SSD capacity increases, the capacity of the DRAMincluded in the SSD also increase, which may increase the cost of theSSD.

A data storage device for enterprise storage systems may be rated basedon a number of drive writes per day (DWPD) for the lifetime of thedrive. A customer may choose to exceed the DWPD of the data storagedevice at the expense of wearing out the device faster. Thus, the costof the data storage device translates to a number of write cycles (e.g.,program erase cycle (PEC)). Because DRAM does not wear out at the samespeed as non-volatile memory, such as NAND memory, large capacity datastorage devices may have uneven memory usage, such that the non-volatilememory may be retired from use before the DRAM is needed to be retiredfrom use.

Therefore, there is a need in the art for an improved storage system forbetter integration into data center environments.

SUMMARY OF THE DISCLOSURE

The present disclosure generally relates to DRAM-less data storagedevices, such as DRAM-less solid state drives (SSDs), and, morespecifically, using external storage devices via an interface betweenthe DRAM-less data storage device and a host device. A storage systemincludes one or more data storage devices, a PCIe switch coupled to theone or more data storage devices, and a controller unit coupled to thePCIe switch. The one or more data storage devices are DRAM-less. Thecontroller unit includes a dynamic random access memory (DRAM) hostmemory buffer (HMB) controller and a DRAM pool or a controller memorybuffer (CMB) controller, a root complex/port, and the DRAM pool. TheDRAM pool includes one or more DRAM devices. The one or more datastorage devices are configured to interact with the controller unit andstore data to a DRAM of the DRAM pool of the controller unit.

In one embodiment, a storage system includes one or more data storagedevices, a PCIe switch coupled to the one or more data storage devices,and a controller unit coupled to the PCIe switch. The one or more datastorage devices are DRAM-less. The controller unit includes a dynamicrandom access memory (DRAM) host memory buffer (HMB) controller and aDRAM pool. The DRAM pool includes one or more DRAM devices.

In another embodiment, a storage system includes a first data storagedevice, a second data storage device, a PCIe switch coupled to the firstdata storage device and the second data storage device, and a controllerunit coupled to the first data storage device and the second datastorage device. The first data storage device and the second datastorage device are DRAM-less. The controller unit includes a dynamicrandom access memory (DRAM) host memory buffer (HMB) controller and aDRAM pool. The DRAM pool includes one or more DRAM devices.

In another embodiment, a storage system includes a first data storagedevice comprising a first memory means, a second data storage devicecomprising a second memory means, a PCIe switch coupled to the firstdata storage device and the second data storage device, and a controllerunit coupled to the first data storage device and the second datastorage device. The first data storage device and the second datastorage device are DRAM-less. The controller unit includes a controllermemory buffer (CMB) controller and a root complex/port.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the presentdisclosure can be understood in detail, a more particular description ofthe disclosure, briefly summarized above, may be had by reference toembodiments, some of which are illustrated in the appended drawings. Itis to be noted, however, that the appended drawings illustrate onlytypical embodiments of this disclosure and are therefore not to beconsidered limiting of its scope, for the disclosure may admit to otherequally effective embodiments.

FIGS. 1A and 1B are a schematic block diagrams illustrating a storagesystem in which a data storage device may function as a storage devicefor a host device, according to certain embodiments.

FIG. 2 is a schematic block diagram illustrating a storage system inwhich an external controller unit may function as a storage device for adata storage device, according to certain embodiments.

FIG. 3 is a schematic block diagram illustrating a storage system inwhich an external controller unit may function as a storage device for afirst data storage device and a second data storage device, according tocertain embodiments.

FIG. 4 is a schematic block diagram illustrating a storage system inwhich an external controller unit may function as a storage device for afirst data storage device and a second data storage device, according tocertain embodiments.

FIG. 5 is a flow diagram illustrating a method of storing data to anexternal controller unit, according to certain embodiments.

FIG. 6 is a flow diagram illustrating a method of reading data from anexternal controller unit, according to certain embodiments.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in oneembodiment may be beneficially utilized on other embodiments withoutspecific recitation.

DETAILED DESCRIPTION

In the following, reference is made to embodiments of the disclosure.However, it should be understood that the disclosure is not limited tospecifically described embodiments. Instead, any combination of thefollowing features and elements, whether related to differentembodiments or not, is contemplated to implement and practice thedisclosure. Furthermore, although embodiments of the disclosure mayachieve advantages over other possible solutions and/or over the priorart, whether or not a particular advantage is achieved by a givenembodiment is not limiting of the disclosure. Thus, the followingaspects, features, embodiments, and advantages are merely illustrativeand are not considered elements or limitations of the appended claimsexcept where explicitly recited in a claim(s). Likewise, reference to“the disclosure” shall not be construed as a generalization of anyinventive subject matter disclosed herein and shall not be considered tobe an element or limitation of the appended claims except whereexplicitly recited in a claim(s).

The present disclosure generally relates to DRAM-less data storagedevices, such as DRAM-less solid state drives (SSDs), and, morespecifically, using external storage devices via an interface betweenthe DRAM-less data storage device and a host device. A storage systemincludes one or more data storage devices, a PCIe switch coupled to theone or more data storage devices, and a controller unit coupled to thePCIe switch. The one or more data storage devices are DRAM-less. Thecontroller unit includes a dynamic random access memory (DRAM) hostmemory buffer (HMB) controller and a DRAM pool or a controller memorybuffer (CMB) controller, a root complex/port, and the DRAM pool. TheDRAM pool includes one or more DRAM devices. The one or more datastorage devices are configured to interact with the controller unit andstore data to a DRAM of the DRAM pool of the controller unit.

FIG. 1A is a schematic block diagram illustrating a storage system 100in which a host device 104 is in communication with a data storagedevice 106, according to certain embodiments. For instance, the hostdevice 104 may utilize a non-volatile memory (NVM) 110 included in datastorage device 106 to store and retrieve data. The host device 104comprises a host DRAM 138 which includes a host memory buffer (HMB) 140.The HMB 140 is a section of the host DRAM 138 allocated for use by acontroller 108 of the data storage device 106. The HMB 140 may storecontrol information, metadata, parity data, error correction code, andother data that may be generally stored in the controller 108 memory orsimilar memory. In some examples, the storage system 100 may include aplurality of storage devices, such as the data storage device 106, whichmay operate as a storage array. For instance, the storage system 100 mayinclude a plurality of data storage devices 106 configured as aredundant array of inexpensive/independent disks (RAID) thatcollectively function as a mass storage device for the host device 104.

The host device 104 may store and/or retrieve data to and/or from one ormore storage devices, such as the data storage device 106. Asillustrated in FIG. 1A, the host device 104 may communicate with thedata storage device 106 via an interface 114. The host device 104 maycomprise any of a wide range of devices, including computer servers,network-attached storage (NAS) units, desktop computers, notebook (i.e.,laptop) computers, tablet computers, set-top boxes, telephone handsetssuch as so-called “smart” phones, so-called “smart” pads, televisions,cameras, display devices, digital media players, video gaming consoles,video streaming device, or other devices capable of sending or receivingdata from a data storage device.

The data storage device 106 includes a controller 108, NVM 110, a powersupply 111, volatile memory 112, the interface 114, and a write buffer116. In some examples, the data storage device 106 may includeadditional components not shown in FIG. 1A for the sake of clarity. Forexample, the data storage device 106 may include a printed circuit board(PCB) to which components of the data storage device 106 aremechanically attached and which includes electrically conductive tracesthat electrically interconnect components of the data storage device 106or the like. In some examples, the physical dimensions and connectorconfigurations of the data storage device 106 may conform to one or morestandard form factors. Some example standard form factors include, butare not limited to, 3.5″ data storage device (e.g., an HDD or SSD), 2.5″data storage device, 1.8″ data storage device, peripheral componentinterconnect (PCI), PCI-extended (PCI-X), PCI Express (PCIe) (e.g., PCIe×1, ×4, ×8, ×16, PCIe Mini Card, MiniPCI, etc.). In some examples, thedata storage device 106 may be directly coupled (e.g., directly solderedor plugged into a connector) to a motherboard of the host device 104.

Interface 114 may include one or both of a data bus for exchanging datawith the host device 104 and a control bus for exchanging commands withthe host device 104. Interface 114 may operate in accordance with anysuitable protocol. For example, the interface 114 may operate inaccordance with one or more of the following protocols: PCI, and PCIe,non-volatile memory express (NVMe), OpenCAPI, GenZ, Cache CoherentInterface Accelerator (CCIX), Open Channel SSD (OCSSD), or the like. Itis to be understood that other protocols not listed may be applicable tothe embodiments described herein. Interface 114 (e.g., the data bus, thecontrol bus, or both) is electrically connected to the controller 108,providing an electrical connection between the host device 104 and thecontroller 108, allowing data to be exchanged between the host device104 and the controller 108. In some examples, the electrical connectionof interface 114 may also permit the data storage device 106 to receivepower from the host device 104. For example, as illustrated in FIG. 1A,the power supply 111 may receive power from the host device 104 viainterface 114.

The NVM 110 may include a plurality of memory devices or memory units.NVM 110 may be configured to store and/or retrieve data. For instance, amemory unit of NVM 110 may receive data and a message from controller108 that instructs the memory unit to store the data. Similarly, thememory unit may receive a message from controller 108 that instructs thememory unit to retrieve data. In some examples, each of the memory unitsmay be referred to as a die. In some examples, the NVM 110 may include aplurality of dies (i.e., a plurality of memory units). In some examples,each memory unit may be configured to store relatively large amounts ofdata (e.g., 128 MB, 256 MB, 512 MB, 1 GB, 2 GB, 4 GB, 8 GB, 16 GB, 32GB, 64 GB, 128 GB, 256 GB, 512 GB, 1 TB, etc.).

In some examples, each memory unit may include any type of non-volatilememory devices, such as flash memory devices, phase-change memory (PCM)devices, resistive random-access memory (ReRAM) devices,magneto-resistive random-access memory (MRAM) devices, ferroelectricrandom-access memory (F-RAM), holographic memory devices, and any othertype of non-volatile memory devices.

The NVM 110 may comprise a plurality of flash memory devices or memoryunits. NVM Flash memory devices may include NAND or NOR-based flashmemory devices and may store data based on a charge contained in afloating gate of a transistor for each flash memory cell. In NVM flashmemory devices, the flash memory device may be divided into a pluralityof dies, where each die of the plurality of dies includes a plurality ofphysical or logical blocks, which may be further divided into aplurality of pages. Each block of the plurality of blocks within aparticular memory device may include a plurality of NVM cells. Rows ofNVM cells may be electrically connected using a word line to define apage of a plurality of pages. Respective cells in each of the pluralityof pages may be electrically connected to respective bit lines.Furthermore, NVM flash memory devices may be 2D or 3D devices and may besingle level cell (SLC), multi-level cell (MLC), triple level cell(TLC), or quad level cell (QLC). The controller 108 may write data toand read data from NVM flash memory devices at the page level and erasedata from NVM flash memory devices at the block level.

The power supply 111 may provide power to one or more components of thedata storage device 106. When operating in a standard mode, the powersupply 111 may provide power to one or more components using powerprovided by an external device, such as the host device 104. Forinstance, the power supply 111 may provide power to the one or morecomponents using power received from the host device 104 via interface114. In some examples, the power supply 111 may include one or morepower storage components configured to provide power to the one or morecomponents when operating in a shutdown mode, such as where power ceasesto be received from the external device. In this way, the power supply111 may function as an onboard backup power source. Some examples of theone or more power storage components include, but are not limited to,capacitors, super-capacitors, batteries, and the like. In some examples,the amount of power that may be stored by the one or more power storagecomponents may be a function of the cost and/or the size (e.g.,area/volume) of the one or more power storage components. In otherwords, as the amount of power stored by the one or more power storagecomponents increases, the cost and/or the size of the one or more powerstorage components also increases.

The volatile memory 112 may be used by controller 108 to storeinformation. Volatile memory 112 may include one or more volatile memorydevices. In some examples, controller 108 may use volatile memory 112 asa cache. For instance, controller 108 may store cached information involatile memory 112 until the cached information is written to the NVM110. As illustrated in FIG. 1A, volatile memory 112 may consume powerreceived from the power supply 111. Examples of volatile memory 112include, but are not limited to, random-access memory (RAM), static RAM(SRAM), flip-flops, and registers.

The data storage device 106 includes a controller 108, which may includethe volatile memory 112. For example, the controller 108 may includeSRAM. Furthermore, the controller 108 may manage one or more operationsof the data storage device 106. For instance, controller 108 may managethe reading of data from and/or the writing of data to the NVM 110. Insome embodiments, when the data storage device 106 receives a writecommand from the host device 104, the controller 108 may initiate a datastorage command to store data to the NVM 110 and monitor the progress ofthe data storage command. Controller 108 may determine at least oneoperational characteristic of the storage system 100 and store at leastone operational characteristic in the NVM 110. In some embodiments, whenthe data storage device 106 receives a write command from the hostdevice 104, the controller 108 temporarily stores the data associatedwith the write command in the internal memory or write buffer 116 beforesending the data to the NVM 110.

FIG. 1B is a schematic block diagram illustrating a storage system 150in which data storage device 106 may function as a storage device for ahost device 104, according to certain embodiments. For simplificationpurposes, common elements between the storage system 100 of FIG. 1A andthe storage system 150 may be referenced by the same reference numeral.The storage system 150 is similar to the storage system shown in FIG.1A. However, in the storage system 150, the data storage device 152includes dynamic RAM (DRAM) 154, whereas in the storage system 100, thedata storage device 106 is DRAM-less. In embodiments described herein,where the DRAM 154 is present, such as in the storage system 150, dataand pointers corresponding to one or more commands may be temporarilystored in the DRAM 154 prior to being processed. It is to be understoodthat the previously exemplified elements that may be stored in the DRAM154 is not intended to be limiting. For example, the DRAM 154 may alsostore data management tables, such as a logical to physical (L2P) table.

However, in embodiments described herein, where the DRAM 154 is notpresent, such as in the storage system 100 where the data storage device106 is DRAM-less, data and pointers corresponding to one or morecommands may be temporarily stored in the HMB 140 or in other volatilememory, such as SRAM. Furthermore, examples of volatile memory 112 ofFIG. 1B, may further include, but not limited to, DRAM and synchronousdynamic RAM (SDRAM (e.g., DDR1, DDR2, DDR3, DDR3L, LPDDR3, DDR4, LPDDR4,and the like)). Thus, the data storage device 106 may be referred to asa DRAM-less data storage device.

FIG. 2 is a schematic block diagram illustrating a storage system 200 inwhich a controller unit 206 may function as a storage device for a datastorage device 212, according to certain embodiments. The data storagedevice 212 may be the data storage device 106 of FIG. 1A, such that thedata storage device 212 is a DRAM-less storage device. The storagesystem 200 includes a host device 202 coupled to a PCIe switch 204. ThePCIe switch 204 is coupled to the controller unit 206 and the datastorage device 212. The PCIe switch 204 may have more than one port,such that more than one data storage device may be connected to the PCIeswitch 204.

The controller unit 206 includes a DRAM host memory buffer (HMB)controller 208 and a DRAM pool 210. In some examples, the DRAM pool 210may resemble a HMB. The controller unit 206 may be a simplified versionof the data storage device 212, where the controller unit 206 isdistinct from the data storage device 212. The DRAM pool 210 includesone or more DRAM devices. In some embodiments, the DRAM pool 210 may beany pool of volatile memory devices.

In some examples, the controller unit 206 may further include an NVMdevice. In cases where power fail protection is needed, the controllerunit 206 may flush data stored in the DRAM pool 210 to the NVM device.In other examples, the controller unit 206 may flush data stored in theDRAM pool 210 to the memory device 222 of the data storage device 212.The DRAM HMB controller 208 may be responsible for allocating one ormore DRAM devices from the DRAM pool 210 to the data storage device 212as well as writing data to and reading from the one or more DRAM devicesof the DRAM pool 210.

The data storage device 212 includes a HMB controller 214, a PCIe/NVMefront end (FE) 216, a memory device management unit 218, a memory deviceinterface unit 220, and a memory device 222, which may be a pool ofmemory devices. The memory device 222 may be an NVM device. When thehost device 202 sends a write command to the data storage device 212,the PCIe/NVMe FE 216 receives the write command. The PCIe/NVMe FE 216may process the write command, which may include generating and encodingerror correction code for the data of the write command. The memorydevice management unit 218 may schedule write commands to program datato the memory device 222 and read commands to read data from the memorydevice 222. The memory device interface unit 220 may access the memorydevice 222 so that data may be programmed to or read from the memorydevice 222.

When data is programmed to the memory device 222, the LBA to PBA mappingof the data may be stored in a L2P table. The controller unit 206 mayappear to the data storage device 212 as a peer PCIe device and may beaddressed using standard PCIe methods. Thus, the HMB controller 214 mayaccess the controller unit 206 as an external storage device in order tostore and retrieve L2P descriptors. For example, the L2P table of thedata storage device 212 may be stored in a DRAM device of the DRAM pool210 rather than a DRAM device of the data storage device 212.

FIG. 3 is a schematic block diagram illustrating a storage system 300 inwhich a controller unit 322 may function as a storage device for a firstdata storage device 306 a and a second data storage device 306 b,according to certain embodiments. Aspects of the storage system 300 maybe similar to the storage system 200 of FIG. 2 , such that the firstdata storage device 306 a and the second data storage device 306 b areDRAM-less. It is to be understood that one or more data storage devicesmay be coupled to the PCIe switch 304 and the controller unit 322.

A host device 302 is coupled to the PCIe switch 304. The first datastorage device 306 a and the second data storage device 306 b eachinclude a first port 308, a second port 310, a HMB controller 312, aPCIe/NVMe FE 314, a memory device management unit 316, a memory deviceinterface unit 318, and a memory device 320, which may be a pool ofmemory devices. The memory device 222 may be an NVM device.

The controller unit 322 includes a DRAM HMB controller 326 and a DRAMpool 324. In some examples, the DRAM pool 324 may resemble a HMB. Thecontroller unit 322 may be a simplified version of the first datastorage device 306 a and the second data storage device 306 b. The DRAMpool 324 includes one or more DRAM devices. In some embodiments, theDRAM pool 324 may be any pool of volatile memory devices (e.g., SRAM,DRAM, or both). In some examples, the controller unit 322 may furtherinclude an NVM device.

The first port 308 may be coupled to the PCIe switch 304 for interactionwith the host device 302. The second port 310 of the first data storagedevice 306 a and the second data storage device 306 b may be used forredundancy (in case the first port 308 fails) or in some embodiments, beconnected to the DRAM HMB controller 326 of the controller unit 322. TheDRAM HMB controller 326 may act as a root complex for one or more datastorage devices. It is to be understood that the data storage devicesmay have more than two ports.

By using the DRAM pool 324 of the controller unit 322 as an externalmemory device, where the second port 310 is coupled to the controllerunit 322, latency may be kept consistent as the second port may be usedfor read and write commands directed to the controller unit 322.Likewise, a PCIe-based prioritization in the PCIe switch 304 may be usedto ensure that accesses to the DRAM pool 324 are prioritized higher thanregular data throughput in order to ensure consistent read access to L2Pentries stored in the DRAM pool 324.

In cases where power fail protection is needed, the controller unit 322may flush data stored in the DRAM pool 324 to the NVM device. In otherexamples, the controller unit 206 may flush data stored in the DRAM pool324 to the memory device 320 of either the first data storage device 306a, the second data storage device 306 b, or both the first data storagedevice 306 a and the second data storage device 306 b. The DRAM HMBcontroller 326 may be responsible for allocating one or more DRAMdevices from the DRAM pool 324 to the first data storage device 306 aand the second data storage device 306 b as well as writing data to andreading from the one or more DRAM devices of the DRAM pool 324.

FIG. 4 is a schematic block diagram illustrating a storage system 400 inwhich a controller unit 402 may function as a storage device for a firstdata storage device 306 a and a second data storage device 306 b,according to certain embodiments. Aspects of the storage system 400 maybe similar to the storage system 300 of FIG. 3 , where the first datastorage device 306 a and the second data storage device 306 b areDRAM-less. For simplification purposes, common elements between thestorage system 400 and the storage system 300 may have identical orsimilar reference numerals.

Rather than using a HMB controller in the controller unit 402, thecontroller unit 402 uses a controller memory buffer (CMB) controller406. The controller unit 402 includes a root complex/port 1 404, whichmay be able to connect to multiple data storage devices, the CMBcontroller 406 coupled to a DRAM pool 408, a PCIe/NVMe FE 410, a memorydevice management unit 412, and a memory device interface unit 414. Insome examples, the controller unit 402 may be a data storage device thatdoes not include an NVM device. In other examples, the controller unit402 may be a data storage device that is reused as a shared DRAMinterface. In some examples, the interconnect to the DRAM pool 408 usesa compute express link, which allows for cache-coherent access betweenmultiple processing devices using PCIe as an interconnect. Thus, thecontroller unit 402 may be a CXL memory device.

FIG. 5 is a flow diagram illustrating a method 500 of storing data to acontroller unit, according to certain embodiments. Method 500 may beemployed by any of the storage systems 200, 300, 400 described above.For exemplary purposes, aspects of the storage system 200 may bereferenced. At block 502, a controller of the data storage device 212,such as the HMB controller 214, determines that an external controllerunit, such as the controller unit 206, is connected to the data storagedevice 212. The connection may be a direct connection or an indirectconnection.

At block 504, the HMB controller 214 receives a DRAM allocation from theDRAM pool 210. For example, the DRAM HMB controller 208 may allocate oneor more DRAM devices from the DRAM pool 210 for use by the data storagedevice 212. At block 506, the HMB controller 214 determines that a writeto a DRAM device is needed. The determination may be due to a write tothe memory device 222, data management operations, such as garbagecollection, to the memory device 222, or the like. Thus, because amapping (LBA to PBA) may be changed, the corresponding L2P entry in thecorresponding L2P table needs to be updated. At block 508, the HMBcontroller 214 sends a write command to the DRAM HMB controller 208 towrite data to the allocated DRAM from the DRAM pool 210 because the datastorage device 212 is a DRAM-less storage device. In embodiments wherethe data storage device does include a DRAM, the HMB controller 214 maystill send a write command to the DRAM HMB controller 208 to write datato the allocated DRAM from the DRAM pool 210 instead of using a DRAM ofthe data storage device that does include a DRAM. Thus, the L2P tablemay be maintained externally, such as in a DRAM of the DRAM pool 210.

FIG. 6 is a flow diagram illustrating a method 600 of reading data froma controller unit, such as the controller unit 206 of FIG. 2 , accordingto certain embodiments. Method 600 may be employed by any of the storagesystems 200, 300, 400 described above. For exemplary purposes, aspectsof the storage system 200 may be referenced. At block 602, a controllerof the data storage device 212, such as the HMB controller 214, receivesa read command from the host device 202 for data stored in the memorydevice 222.

At block 604, the HMB controller 214 locates a L2P table in thecontroller unit 206 corresponding to the data storage device 212. Atblock 606, the HMB controller 214 sends a read command to the DRAM HMBcontroller 208 to retrieve data from the L2P table corresponding to theread command. At block 608, the data is read from the memory device 222using the retrieved L2P table information and the data is delivered tothe host device 202.

By having a storage system that includes an external controller unit orstorage device for use as a volatile memory pool for one or more datastorage devices, the cost of the one or more data storage devices may bedecreased due to a decreased or non-existent volatile memory requirementof the one or more data storage devices.

In one embodiment, a storage system includes one or more data storagedevices, a PCIe switch coupled to the one or more data storage devices,and a controller unit coupled to the PCIe switch. The one or more datastorage devices are DRAM-less. The controller unit includes a dynamicrandom access memory (DRAM) host memory buffer (HMB) controller and aDRAM pool. The DRAM pool includes one or more DRAM devices.

The PCIe switch is directly coupled to the DRAM HMB controller. Eachdata storage device of the one or more data storage devices includes aHMB controller, a PCIe/NVMe front end unit, a memory device managementunit, a memory device interface unit, and a memory device. Thecontroller unit acts as a root complex for the one or more data storagedevices. The one or more data storage devices are distinct from thecontroller unit. The controller unit appears as a peer PCIe device tothe one or more data storage devices. The DRAM pool is shared by the oneor more data storage devices. The one or more data storage devices istwo or more data storage devices. Each data storage device of the one ormore data storage devices includes a first port and a second port. Thefirst port is coupled to the PCIe switch.

In another embodiment, a storage system includes a first data storagedevice, a second data storage device, a PCIe switch coupled to the firstdata storage device and the second data storage device, and a controllerunit coupled to the first data storage device and the second datastorage device. The first data storage device and the second datastorage device are DRAM-less. The controller unit includes a dynamicrandom access memory (DRAM) host memory buffer (HMB) controller and aDRAM pool. The DRAM pool includes one or more DRAM devices.

The first data storage device and the second data storage device eachhave a first port and a second port. The first port is coupled to thePCIe switch. The second port is coupled to the controller unit. Thesecond port is coupled to a HMB controller. The HMB controller isdisposed in the first data storage device and the second data storagedevice. The second port is coupled to the DRAM HMB controller. Thecontroller unit is configured to, upon detecting a power failure eventof the controller unit, push data of the DRAM pool to either the firstdata storage device, the second data storage device, or both first datastorage device and the data storage device.

In another embodiment, a storage system includes a first data storagedevice comprising a first memory means, a second data storage devicecomprising a second memory means, a PCIe switch coupled to the firstdata storage device and the second data storage device, and a controllerunit coupled to the first data storage device and the second datastorage device. The first data storage device and the second datastorage device are DRAM-less. The controller unit includes a controllermemory buffer (CMB) controller and a root complex/port.

The first data storage device, the second data storage device, and thecontroller unit each includes a memory means interface, a memory meansmanagement unit, and a PCIe/NVMe front end unit. The first data storagedevice and the second data storage device each includes a first port anda second port. The first port is coupled to the PCIe switch. The secondport is coupled to the root complex/port. The CMB controller is coupledto a DRAM pool.

While the foregoing is directed to embodiments of the presentdisclosure, other and further embodiments of the disclosure may bedevised without departing from the basic scope thereof, and the scopethereof is determined by the claims that follow.

What is claimed is:
 1. A storage system, comprising: one or more datastorage devices, wherein the one or more data storage devices areDRAM-less; a PCIe switch coupled to the one or more data storagedevices; and a controller unit coupled to the PCIe switch, thecontroller unit comprising: a dynamic random access memory (DRAM) hostmemory buffer (HMB) controller; and a DRAM pool, wherein the DRAM poolcomprises one or more DRAM devices.
 2. The storage system of claim 1,wherein the PCIe switch is directly coupled to the DRAM HMB controller.3. The storage system of claim 1, wherein each data storage device ofthe one or more data storage devices comprises: a HMB controller; aPCIe/NVMe front end unit; a memory device management unit; a memorydevice interface unit; and a memory device.
 4. The storage system ofclaim 1, wherein the controller unit acts as a root complex for the oneor more data storage devices.
 5. The storage system of claim 1, whereinthe one or more data storage devices are distinct from the controllerunit.
 6. The storage system of claim 1, wherein the controller unitappears as a peer PCIe device to the one or more data storage devices.7. The storage system of claim 1, wherein the DRAM pool is shared by theone or more data storage devices.
 8. The storage system of claim 1,wherein the one or more data storage devices is two or more data storagedevices.
 9. The storage system of claim 1, wherein each data storagedevice of the one or more data storage devices comprises a first portand a second port, and wherein the first port is coupled to the PCIeswitch.
 10. A storage system, comprising: a first data storage device; asecond data storage device, wherein the first data storage device andthe second data storage device are DRAM-less; a PCIe switch coupled tothe first data storage device and the second data storage device; and acontroller unit coupled to the first data storage device and the seconddata storage device, the controller unit comprising: a dynamic randomaccess memory (DRAM) host memory buffer (HMB) controller; and a DRAMpool, wherein the DRAM pool comprises one or more DRAM devices.
 11. Thestorage system of claim 10, wherein the first data storage device andthe second data storage device each have a first port and a second port,and wherein the first port is coupled to the PCIe switch.
 12. Thestorage system of claim 11, wherein the second port is coupled to thecontroller unit.
 13. The storage system of claim 12, wherein the secondport is coupled to a HMB controller.
 14. The storage system of claim 13,wherein the HMB controller is disposed in the first data storage deviceand the second data storage device.
 15. The storage system of claim 12,wherein the second port is coupled to the DRAM HMB controller.
 16. Thestorage system of claim 10, wherein the controller unit is configuredto, upon detecting a power failure event of the controller unit, pushdata of the DRAM pool to either the first data storage device, thesecond data storage device, or both first data storage device and thedata storage device.
 17. A storage system, comprising: a first datastorage device comprising a first memory means; a second data storagedevice comprising a second memory means, wherein the first data storagedevice and the second data storage device are DRAM-less; a PCIe switchcoupled to the first data storage device and the second data storagedevice; and a controller unit coupled to the first data storage deviceand the second data storage device, the controller unit comprising: acontroller memory buffer (CMB) controller; and a root complex/port. 18.The storage system of claim 17, wherein the first data storage device,the second data storage device, and the controller unit each comprises:a memory means interface; a memory means management unit; and aPCIe/NVMe front end unit.
 19. The storage system of claim 17, whereinthe first data storage device and the second data storage device eachcomprises a first port and a second port, wherein the first port iscoupled to the PCIe switch, and wherein the second port is coupled tothe root complex/port.
 20. The storage system of claim 17, wherein theCMB controller is coupled to a DRAM pool.